Updating parameters in a bridged multistandard home network

ABSTRACT

The invention relates to the field of home networks, in particular to the connection of two home networks of different types via a gateway. The network appliances in the network of the first type are also intended to be able to control the network appliances in the network of the second type, and vice versa. One problem that occurs when carrying out conversion processes on control messages is that an input parameter which is known in the network of the first type can be changed as required and can also be signaled further within this network, but the associated correspondence in the network of the second type is permanently set, and accordingly cannot be changed. The invention provides a way in which an input parameter such as this can nevertheless be likewise updated in the network of the second type.

This application is a divisional of U.S. application Ser. No.10/542,585, filed Jan. 6, 2006 now U.S. Pat. No. 7,865,622, hereinincorporated by reference.

The invention relates to the technical field of home networks. Inparticular the invention resides in the area where a network of a firsttype, for example an HAVi-based home network, is connected to a networkof a second type, for example UPnP-based home network, via a gateway.

BACKGROUND OF THE INVENTION

Various home network standards have now become available for networkingof appliances in the domestic area. In particular, the IEEE 1394 busstandard has become established in the field of entertainmentelectronics. This allows communication between the entertainmentelectronic appliances at a very high data rate. Data rates of 100, 200and 400 Mbit/s are supported. This is sufficient to transmitasynchronous data packets for controlling the network stations, as wellas isochronous audio and video data streams, in parallel. IEEE Standard1394, however, specifies only the lower layers of the ISO/OSI referencemodel for data communication, that is to say the bit transmission layer(physical layer), the data protection layer (Data Link Layer) and partsof the switching layer (Network Layer). The higher layers, that is tosay the transport layer, the communication control layer (SessionLayer), the presentation layer and the application layer, are, however,unspecified.

A consortium of entertainment electronics companies have also taken onthe task of defining the higher layers for interchanging data betweenentertainment electronic appliances. This standard is known by theabbreviation HAVi, where HAVi stands for Home Audio/Videointeroperability. This standard specifies a so-called InteroperabilityMiddleware, which ensures that products from different manufacturersunderstand one another, that is to say cooperate in order to carry outtasks together via the network.

Another consortium of companies, in particular the computer industrycompanies led by Microsoft, have started a different initiative forspecification of network control software based on the existing InternetProtocol (IP). This network system has become known by the abbreviationUPnP (Universal Plug and Play). In this system, the specification doesnot relate primarily to entertainment electronic appliances, but otherappliances can also be integrated in the network, in particular such aspersonal computers, domestic appliances in the white good range, such asrefrigerators, microwave cookers, washing machines, heating controllers,light controllers, alarm system controllers, etc.

Even though the two home network standards HAVi and UPnP are sometimesregarded as competitors, at least in part they serve a different purposeand a scenario is presupposed in which the two networks can existalongside one another in a domestic environment, and are connected toone another via a gateway. It should then be possible to control theappliances in the UPnP network from the HAVi network side, and viceversa. The connection unit between the two networks is referred to inthe following text as a gateway. The expression gateway is frequentlynot the same as the other expression bridge circuit or bridge, which islikewise used. In some cases, however, the difference between a bridgecircuit and a gateway is that a bridge circuit transmits the datapackets on the data protection layer to the respective other networkwhile, in contrast, in the case of a gateway, the data packets are infact transmitted at a higher level in the ISO/OSI reference model.

The work so far relating to gateways for the connection of HAVi and UPnPnetworks has always been based on a so-called “proxy-based gateway”approach. This conceals the following: in order that the UPnP networkstations are visible from an HAVi appliance, the UPnP appliances arerepresented on the HAVi side in the gateway by so-called HAVi-DCMs. DCMin this case stands for Device Control Module. These additional DCMs arethen logged in the HAVi network and can be addressed from the HAViappliances. One DCM is in this case required for each UPnP networkstation. If the network station offers different functionalities, suchas a television which has the function of a tuner, of an amplifier andof a display unit, then a number of so-called FCMs may be provided foreach DCM. An FCM is in this case a so-called functional componentmodule, by means of which an appliance functionality is thus covered.

Conversely, the HAVi network stations should also be addressed from theUPnP side. On the UPnP side, an HAVi appliance is represented by aso-called UPnP device. This means that a corresponding UPnP device isalso provided in the gateway for each HAVi network station. A so-calledXML appliance description exists for each UPnP device. In this case, XMLstands for the description language Extension Markup Language. Thecorresponding feature for an HAVi FCM on the UPnP side is a so-calledservice. A number of UPnP services can thus be described in one UPnPdevice. The conversion between HAVi DCM/FCM and UPnP devices/servicesshould be as complete as possible. However, if the two standards arecompared, it is evident that such complete conversion is not alwayspossible.

UPnP appliances invariably originate from areas beyond entertainmentelectronic appliances, so that the functionalities of such appliances,such as a washing machine, cannot easily be mapped onto the normalfunctionalities of entertainment electronic appliances. How this cannevertheless still be successfully accomplished for the representationof UPnP appliances on the HAVi side is evident from the previousEuropean Patent Application EP 02 090 147.6 from the same applicant.

INVENTION

During the development work relating to the merging of the differenthome networks on an HAVi and UPnP basis, the inventor encountered aproblem in that complete one-to-one conversion between HAVi and UPnPfunctionalities is likewise not possible. On the HAVi side, afunctionality such as this is the capability to allocate a user-definedname to an HAVi network station. This can be chosen freely by the user,and can also be changed retrospectively. The HAVi specification in thiscontext states that the parameter UserPreferredName can be defined foreach appliance. If this appliance name is changed, then the changes aresignaled via so-called events to all the other HAVi network stationswhich then make the appropriate change visible, if they are equippedwith a display unit. If the changed appliance name is also intended tobe visible on the UPnP side, then the parameter UserPreferredName mustbe mapped onto a corresponding information element in the associated XMLappliance description. The only element which may be used for thispurpose on the UPnP side has the designation “FriendlyName” and is partof the XML appliance description. The UPnP specification is, however,predicated on the XML appliance descriptions being documents that cannotbe changed. Specifically, there is no capability to inform UPnPappliances that, for example, the previously instantiated XML appliancedescription has changed and, so to speak, should therefore be updatedfor the UPnP appliances.

Nevertheless, the invention has the aim of providing the capability tomake the changed appliance names consistently visible between thenetworks. The solution according to the invention comprises the UPnPnetwork stations being forced once again to read the updated XMLappliance description by the HAVi network station whose appliance namehas been changed logging off and then logging on once again.

A software module is advantageously provided at the gateway, whichevaluates the appliance name change event and then ensures that thelogging-off message is sent to the UPnP side, initiating thereinitialization of the associated XML description and ensuring that themessage for the appropriate HAVi appliance to log on again is sent tothe UPnP side. In particular, the discovery message of the ssdp::byebyetype can advantageously be used as the logging-off message. Thediscovery message of the ssdp::alive type can advantageously be used asthe logging-on message. The information element in the XML appliancedescription which best represents the appliance name has the designationFriendlyName on the UPnP side.

One advantageous development of the invention provides for a text inputmenu to be provided for user-defined inputting of the appliance name,with this menu being overlaid on a display unit on the HAVi side, andwhich is designed such that the text can be input with the aid of thenumber keys on a remote control.

DRAWINGS

Exemplary embodiments of the invention will be explained in more detailin the following description and are illustrated in the drawings, inwhich:

FIG. 1 shows an illustration of two home networks which are connected toone another via a gateway;

FIG. 2 shows the procedure for the method according to the invention,and the interaction of the software components in the HAVi appliancewhose appliance name is changed, and in the gateway, and;

FIG. 3 shows the text input menu according to the invention.

DESCRIPTION OF THE INVENTION

FIG. 1 shows the basic structure of two home networks which areconnected to one another via a gateway. A UPnP-based home network isshown in the left-hand side of FIG. 1. The reference number 10 denotes amonitoring camera, as an example of a UPnP appliance. The referencenumber 11 denotes a light control unit, as a further example of a UPnPnetwork station. The reference number 12 also denotes a personalcomputer, which is likewise integrated in the UPnP network. The UPnPappliances are linked via a network connection 13. The widely used andknown Ethermet Bus should be mentioned as a typical example of a networkconnection 13 such as this.

An example of a home network which is designed in accordance with theHAVi standard is shown on the right-hand side of FIG. 1. The referencenumber 19 denotes a so-called set-top box, which is a receiver fordigital television. The reference number 20 denotes a digital TV.Digital televisions such as these typically no longer have their ownreceiving section, but receive the digital video and audio data fromsome other appliance, for example from the set-top box 19. In theillustrated situation, the video and audio data is, however, transportedvia the network cable to the digital television 20. The reference number21 denotes a video recorder. The network cable is marked by thereference number 22. In the assumed example of an HAVi network, thisnetwork cable 22 is formed by the so-called IEEE 1394 bus.

The gateway 14 is illustrated in the center of FIG. 1 and connects thetwo networks to one another. For this purpose, on the one hand aso-called IP stack 15 and on the other hand a so-called HAVi stack 16are provided in the gateway 14. The IP stack 15 and the HAVi stack 16contain all of the software components which are required forparticipation in the respectively connected network. In addition, thegateway 14 contains further software components, which are not listedseparately. However, the illustration shows schematically that data isinterchanged between the two software stacks 15 and 16. The referencenumber 17 in this case denotes the data path for the audio and videodata streams. The reference number 18, in contrast, denotes the datapath for the control messages which need to be exchanged between the twosoftware stacks.

The HAVi standard as well as the UPnP specification have been published.Version 1.1 of the HAVi specification is now available. The precisetitle is: The HAVi Specification “Specification of the Home Audio/Videointeroperability (HAVi) Architecture”, Version 1.1, 15 May 2001. TheUPnP specification can be obtained from the company Microsoft. Furtherinformation is also available on the official Internet page for the UPnPsystem. For this purpose, reference should be made to the Internet pagewww.UPnP.org.

Since the components of the HAVi system and of the UPnP system are notall important in order to explain the present invention, only theessential components will be explained in more detail in the followingtext. For further details relating to the disclosure of the invention,express reference is made to the two specifications mentioned above.

In FIG. 2, the same reference numbers denote the components which arealso illustrated in FIG. 1. The major software components of the gateway14 are shown on the left-hand side of FIG. 2. The major softwarecomponents of the digital television 20 are shown on the right-hand sideof FIG. 2. As has already been explained with reference to FIG. 1,gateway 14 contains an Internet Protocol stack 15 for communication inthe UPnP network, and an HAVi stack 16 for communication in the HAVinetwork. The IEEE 1394 interface 41 is shown on the lowermost level ofthe HAVi stack 16. This is typically not in the form of a softwarecomponent. In fact, the IEEE Standard 1394 stipulates that both the bittransmission layer and the data protection layer must be in the form ofhardware. Two separate ICs are typically used for this purpose.Furthermore, the so-called communication media manager 40 is in the formof a software component. This forms parts of the switching layer and ofthe transport layer, and forms an interface between the other softwareelements and the IEEE 1394 bus. The so-called messaging system 39 isimplemented above the communication media manager 40. In the HAVistandard, this component is a very important component, since themessaging system is used whenever two different software modules wish tointerchange data with one another. The messaging system is independentof the network and transport layer in the ISO/OSI reference model.

A further module in the HAVi stack is a so-called event manager 34. Theobject of the event manager 34 is to inform the various softwareelements in the network of changes/events which have occurred. Eventssuch as these occur in particular when an appliance is added to thenetwork or is disconnected from the network. A further softwarecomponent of the HAVi stack 16 is a so-called registry 35. The availablesoftware elements of the network are listed in the registry. Theregistry offers the service of searching for specific software elements.A software element which wishes to communicate with other softwareelements in the network must be registered in the registry. A furthersoftware element in the HAVi stack 16 is a so-called DCM manager 36whose object is to install the DCMs (Device Control Modules) in therespective network station.

Applications which are implemented in the network access a number ofso-called FCMs (Functional Component Modules). The functionalities ofvarious types of FCMs are specified in the HAVi standard itself. Theseinclude a tuner FCM, VCR FCM, Clock FCM, Camera FCM, AV Disc FCM,Amplifier FCM, Display FMC, AV Display FCM, Modem FCM and Webproxy FCM.

The resource manager 37 has the task of monitoring whether specificresources in the network are still available for a respectivelydemanding task, or whether they have already been allocated. It thusallocates appropriate resources to the application programs, providedthat they are free.

A so-called stream manager 38 is also provided as a further component inthe HAVi stack, and is responsible for setting up connections betweennetwork subscriber stations. AV data streams can then be transmitted viathe connections which have been set up.

Various DCM modules are also set up in the gateway, above the softwareelements, which have already been described, on the HAVi stack. A DCM isa software element which is used on the HAVi side in order to control acorresponding HAVi appliance. An associated HAVi DCM is thereforeinstalled in the gateway for each UPnP appliance, in order to controlthe UPnP appliances. By way of example, the reference number 30 denotesthe DCM for the monitoring camera 10 in the UPnP network. The DCM 31 isused to control the personal computer 12 in the UPnP network. Anassociated DCM 33 is also provided in the HAVi gateway 14 for the lightcontrol unit 11. In accordance with the HAVi specification, the otherDCMs in the HAVi network can also be installed in the HAVi gateway 14,but need not be, as is shown in the example in FIG. 2. Reference number32 also denotes the application program for the gateway 14. Thefunctions which this module carries out will be explained in more detailin the following text.

The IP stack 15, which is likewise provided in the gateway 14, is notshown with all its components. The configuration of an IP stack such asthis is known from the prior art. Only three major components aretherefore illustrated, in order to simplify the illustration. The firstof these is a so-called HTTP Webserver 27 which contains the various XMLappliance descriptions for the appliances in the HAVi network, that isto say an XML appliance description 23 for the video recorder 21, an XMLappliance description 24 for the set-top-box 19, and an XML appliancedescription 25 for the digital television 20. A unit to implement theSSDP protocol is also provided as a further component of the IP stack15, and is annotated by the reference number 29. The SSDP Protocol(Simple Service Discovery Protocol) is likewise assumed to be known. Afurther component is also an XML appliance description production unit28. This is also regarded as a conventional implementation for thegateway technology that is available nowadays. The component need not beregarded as part of the IP stack 15, and can also be implemented as aunit separated from it.

The individual software elements of the HAVi stack are likewise listedseparately for the digital television 20. Since these components areannotated by the same letter abbreviations as those in the HAVi stack 16in the gateway 14, there is no need to explain these parts once again indetail.

The digital television 20 in the exemplary embodiment is assumed to be aso-called FAV appliance (Full AV Device). An appliance such as this isequipped with a very large number of HAVi software elements. The specialfeature is that an FAV appliance also has a so-called Java virtualmachine integrated in it. The appliance is thus able to convert Javacode to program code that can be run, and then to run it in anappropriate manner. An FAV appliance has the capability to load a DCMfrom some other HAVi network appliance. The DCM is then installed in theFAV appliance together with the DCM for the FAV appliance. FIG. 2therefore shows that the DCMs 43 and 45 for controlling the videorecorder 21 and the set-top-box 19 are also installed together with theDCM for the digital television 44. The illustration likewise also showsa user interface 42.

The way in which the various software elements interact when theuser-defined appliance name for the digital television 20 is changed inthe HAVi network will now be described in detail in the following text.The input parameter UserPreferredName is provided in the HAVi system inorder to identify a user-defined appliance name. This parameter is partof every DCM. However, the parameter is also stored, for example, in theregistry for the respective appliance. The user would like to allocate aunique name to the individual appliances in the network. If there aretwo or more appliances in the same category in the network, for examplea television which is located in the living room and a television in thebedroom, then it should easily be possible to distinguish between theseappliances. For example, for this purpose, the user can give the name“living room TV” to the television in the living room. Once he hasentered the name via the user interface, the user interface 42 willinform the DCM for the digital television 20, with the assistance of themessaging system 51, that a new input parameter UserPreferredName hasbeen entered for the television, marked with the label {circle around(1)}. For this purpose, the user interface 42 uses the serviceDCM::SetUserPreferredName which is available in the DCM. In addition toupdating the parameter in the DCM itself, this service also initiatesthe reregistration of the new name in the registry 47, which isidentified by the label {circle around (2)}. Once all of the entriesrelating to this parameter have been updated, the DCM 44 then initiatesa notification to the event manager 46. This step is marked by the label{circle around (3)}, and is carried out by the DCM 44 generating aso-called UserPreferredNameChangedEvent. Since this event is classifiedas a global event within the HAVi system, this results in the eventmanager 46 passing on this event. The label {circle around (4)} denotesthe notification of the gateway 14 via the UserPreferredNameChangedEventfor the digital television 20. All of the software elements of thegateway 14 which are of interest to this event have been registered inthe event manager 34.

Specifically, the gateway software module 32 for the event manager 34has been able to register for the UserPreferredNameChanged Event. Theevent manager 34 will then inform the gateway software 32 of the arrivalof the UserPreferredNameChangedEvent relating to the digital television20, see the label {circle around (5)}. Notification of the gatewaysoftware 32 then leads to the emission of a notification to the UPnPprotocol stack 15 for the gateway. This is identified by the mark{circle around (6)} in FIG. 2. Since the UPnP protocol stack 15 doesnot, however, accept any specified HAVi messages, the gateway software32 has to initiate a translation of this message to the format which theUPnP stack 15 can understand. The associated UPnP message which can beunderstood by the UPnP stack 15 may be based on the so-called SOAPprotocol (Simple Object Access Protocol). The gateway software 32therefore has to initiate, or itself carry out, a conversion of the HAVimessage to the form of an SOAP message. Since both systems arespecified, this conversion could be carried out without any furtherdifficulties. The SSDP unit 29 then converts the corresponding SOAPmessage based on the SSDP protocol to an SSDP discovery message.Alternatively, this may also be implemented in such a way that thegateway software 32 informs the software module which represents theHAVi appliance as a UPnP appliance of the change to the name. Thismodule then uses the SSDP module 29 to generate the discovery messagessdp::byebye(DTV), which is passed on in the UPnP network to all of thesubscriber stations. This is identified by the mark {circle around (7)}.

This notification results in the digital television 20 logging off inthe UPnP network. This means that a UPnP appliance which is currentlydisplaying the network structure completely, including the HAViappliances, on a display unit will briefly mask out the digitaltelevision 20 from the display. Once the digital television 20 haslogged off, the gateway software 32 then ensures in the step marked bythe mark {circle around (8)}. that the XML appliance descriptionproduction unit 28 generates a new XML description for the digitaltelevision 20. This is done by the software module 32 replacing the old“FriendlyName” by the new “UserPreferredName”, which is received foreach event, in the XML document and replacing the old XML description 25on the Webserver 27 by the new one. The associated step is identified bythe mark {circle around (9)}.

Once the new appliance description has been produced, the gatewaysoftware 32 once again produces an SOAP message for the SSDP module 29,label {circle around (10)}. This SOAP message is converted by the SSDPmodule to an SSDP discovery message, to be precise this being thessdp::alive(DTV) message. The digital television 20 once again uses thismessage to log on in the UPnP network once again, label {circle around(11)}. The conversion of the DCM 44 to the associated XML description 25takes only a short time, for example a few milliseconds. The logging-onmessage is therefore likewise transmitted only a short time after thelogging-off message to the UPnP network. The logging-off of the DTVappliance 20 in the meantime is therefore not perceived, or is scarcelyperceived, by the user. When the digital television 20 logs on again,the UPnP appliances are requested to once again load the XML descriptionfor the digital television 20. Once this process has been completed, thenew appliance name is also updated in the UPnP network and is taken intoaccount in the display, that is to say the new appliance name will bedisplayed on the respective display unit.

This procedure ensures the consistency of naming between networks. Theprocedure comprising the HAVi appliance previously logging off and thenlogging on again ensures that the name of an HAVi network appliance isnever inconsistent in any phase.

The following text also provides an explanation of how the text inputfor a text field can advantageously be entered in a user interface bymeans of a conventional remote control. FIG. 3 shows a text input menuaccording to the invention, which is identified by the reference number60 in the figure. The illustration likewise shows a text field withinthe user interface for controlling the digital television 20 that islocated in the HAVi network. This text field is provided with thereference number 61 which corresponds to the input field for the inputparameter UserPreferredName. The illustration shows that the standardentry TV is currently entered in this field. Once the user has focusedthis text field, that is to say has selected it using the remotecontrol, the input menu 60 is started by pressing the “text input key”on the remote control. After pressing the “text input key” on the remotecontrol, a check is carried out to determine whether a text input fieldis focused which may be located in a havlet, an application or in theFAV's own UI.

The text input menu appears in the form of a window on the display unitfor the television. A larger text input window 62 is provided within thetext input menu 60. The normal keys of a remote control are symbolizedalongside this text input window. These include the number keys, thecursor control keys, a selection key and the different colored keyswhose importance is in each case indicated in abbreviated form alongsidethe colored symbol. The symbols above the number keys in each case showwhich letters can be selected using that number key for a text input.The text is therefore input simply by means of a remote control via thenumber keys, for example in the form that is known from mobiletelephones. In this context, it is also possible to integrate automaticword identification in the text input tool. For example, the wordidentification system T9 is also used in mobile telephones. As isillustrated in FIG. 3, once the text input menu has been openedautomatically, the current content of the focused text field isautomatically copied into the text input field 62. The blinking of acursor underneath this then indicates that the individual letters in thestandard entry can be changed. Once the new name has been entered, thenew entry is copied into the text field 61 by pushing the input key OK.If “OK” in the “text input tool” is pressed, the amended text is copiedto the text input field 61, and is focused. This thus results once againin the same state as before the text input, but with the text in thetext input field having been changed. In order to end the text input,“OK” must be pressed once again. In the state before starting and afterending the “text tool”, a correct keypad can be used to enter text orelse to enter numbers via the number keys of the remote control.

The text input tool may be in the form of a central tool within the HAViUI 42 of the digital television 20. The text input tool is provided forthe situation in which no keypad is actually delivered for the digitaltelevision, but only a normal remote control. The programming conversionfor this text input aid can be carried out as follows. The HAVi userinterface 42 monitors whether the text key of the remote control hasbeen pressed. In this case, the only keys which are shown in the textinput tool are those which are necessary for inputting text. Since thetext key is used before the text tool is started and is no longer neededafter this, it is no longer illustrated in FIG. 3.

After pressing the “text input key” on the remote control, a check iscarried out to determine whether a text input field is focused, whichmay be located in a havlet, an application program or in the FAV's ownuser interface program.

After completion of the text input, the text input tool is ended, andthe newly edited text is copied to the previously focused text inputfield. This is thus a universal text input aid, which can be used forall havlets/applications in the HAVi network.

The invention may be used in particular for a gateway which is used forconnection of an HAVi network to a UPnP network. However, it is alsofeasible to use it for gateways which connect other networks to oneanother, for example an HAVi network to an OSGi network or a networksuch as EHS which is based on powerline data transmission to an IPnetwork such as UPnP or OSGi.

1. A connection unit for connection of a network of a first type to anetwork of a second type, wherein the connection unit is an electronicdevice, having logging-off means which, when the information relating tothe change to an input parameter for a network station in the network ofthe first type is input, perform logging-off of the network stationwhich relates to the input parameter in the network of the second type,the connection unit having conversion means for conversion of thechanged input parameter to a format which is suitable for the network ofthe second type, and having logging on means which, after conversion ofthe input parameter, once again perform logging-on of the networkstation which relates to the changed input parameter in the network ofthe second type, wherein the logging-off and logging-on again means areadapted to carry out said logging-off and logging-on in accordance withthe Simple Service Discovery Protocol SSDP, in particular using thessdp::byebye logging-off message and the ssdp::alive logging-on message.2. The connection unit as claimed in claim 1, according to which theconnection unit is adapted to support as the network of the first type anetwork which is based on an international standard called HAViStandard, where HAVi stands for Home Audio/Video Interoperability. 3.The connection unit as claimed in claim 2, in which the input parameteris a HAVi defined parameter called UserPreferredName, which correspondsto the user defined name of a HAVi network station.
 4. The method asclaimed in claim 3, in which the input parameter UserPreferredName ismapped onto the information element FriendlyName of an XML appliancedescription for the HAVi network station which relates to the inputparameter.